Shops

For these integrations, the root entity is the shop. All shop platform operations require that you first have a shop. To create one you can use the create shop endpoint to create a shop. The ext_shop_id must be unique within each Pio organization and should be set to something that your integration can use to uniquely idenfity the shop. This ext_shop_id will be included in webhook requests to identify the intended target shop.

Each product and order you create later will be assosiated with a shop.

How many shops you need to create in Pio depends on the operation. In some cases, one might be enough, but in many cases there could be advantages of creating several. This is something you should keep in mind when creating the integration. First off, one integration can serve several shops. Once the integration is created, running the authorization flow several times creates more tokens which can each be used towards new shops. Each new shop should be created with an earlier unused token.

So, in which cases might you need several shops? One advantage of having several shops is that picking can be split up by shop. This means you can select to only pick for one shop at picking time, but of course not only limited to. Maybe you have multiple brands or order channels, this could make sense to send into different shops in Pio.

Another advantage of having several shops is later being able to prioritize orders based on which shop they belong to. Say you have Brand A which you want to send out quicker than Brand B. One way to solve this could be to send these order into separate shops and in Pio you can create a order priority which prioritizes one shop over the other.